Why care plans fail, and how to keep them alive
A plan written once and filed away is a document, not a plan. Keeping it alive means making it the thing the team reads every morning.
Theo Marsh
Product, Thrive
Every practice has a folder of care plans that were written with care and never opened again. The plan was fine. The problem is that it lived somewhere the team does not look.
A plan is a promise about tomorrow
A care plan says: on day two we call, on day seven we review, if pain goes above four we escalate. Those are appointments and tasks with dates attached. If they exist only as prose in a document, they depend on someone remembering to read the document on the right day. Nobody does that reliably, and it is not a character flaw. It is a filing system.
Turn the prose into the schedule
The plans that survive are the ones that get decomposed the moment they are written:
- Every dated step becomes a task assigned to a role, not a person, so it survives a shift swap.
- Every threshold becomes a rule — "if the check-in reply reports pain above four, create an urgent follow-up".
- Every document is tagged by pathway, so the post-op plan for one patient is one click from every other post-op plan.
Make it the morning read
The last piece is cultural, and software can only support it. The team needs one screen it opens at the start of the day, and the plan's tasks need to be on it. In Thrive that is the Tasks tab beside the day's schedule. The medium does not matter much. The habit does: if the plan is not on the screen the team already reads, it is not really a plan.
We used to write beautiful plans and then run the day from memory. Now the plan runs the day.A medical director, quoted with permission
Review the plan, not just the patient
Plans should be versioned. When a step is skipped or a threshold is adjusted, the change should be visible and the reason recorded. Over a quarter, the versions become the best evidence you have about which pathways work and which ones only look good on paper.
Write the plan once, decompose it into the schedule, and keep the versions. That is the whole discipline. Everything else is a folder.